da_describe_endpoint

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden, but the verb 'Show' accurately conveys a read-only metadata lookup and the Args clarify that no operation is executed. It does not add details like error behavior or authentication, but for an introspection tool the described behavior is transparent and unambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

One clear leading sentence and two terse parameter lines carry exactly the needed information. There is no filler, and the most important scoping ('one New API operation') is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter metadata lookup with an output schema, the definition is nearly complete. The main missing piece is pointing the agent to da_list_endpoints for discovering valid method/path combinations, but nothing else an agent needs to call it is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the Args lines compensate by defining method as 'HTTP method' and path as a 'Path template' with a concrete placeholder example. This is meaningful but not exhaustive: valid HTTP methods and path-source guidance are not provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and object: 'Show parameters for one New API operation.' This distinguishes it from siblings like da_list_endpoints (which lists operations) and da_api/da_legacy, and the method/path args complete the contract.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'one New API operation' implies it is for a single endpoint rather than enumeration, and the method/path inputs make that concrete. However, it does not explicitly say when to prefer this over da_list_endpoints or state exclusions, leaving usage conditions to be inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.