discord_get_endpoint

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

Annotations already declare readOnlyHint=true, and the description adds 'normalized schema' indicating a read/transform operation. It does not describe behavior for invalid endpoints or pagination, but annotations cover the safety profile, so the description adds modest context.

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?

The description is a single, well-structured sentence with no filler. It is front-loaded with the verb and resource, earning every word.

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 simple single-parameter tool with annotations and no output schema, the description is adequate but leaves gaps: no endpoint format guidance and no indication of return structure beyond 'normalized schema.' Sibling names help, but the description itself is minimal.

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 coverage is 0%, so the description must explain the 'endpoint' parameter. It only says 'Discord Bot endpoint,' which does not clarify expected format (e.g., path, name, ID). The param name is somewhat self-explanatory but lacks critical detail for correct invocation.

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 uses a specific verb 'Return' and a resource 'normalized schema for one Discord Bot endpoint,' which clearly differentiates from siblings like discord_search_endpoints (search) and discord_call_endpoint (execute). It is concise and unambiguous.

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 description implies usage for retrieving a single endpoint's schema, but does not explicitly state when to choose this over siblings. No exclusions or alternatives are named; however, the word 'one' hints at distinct use from search or refresh.

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