Discover Endpoints in a Category

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

Annotations already declare readOnly, non-destructive, idempotent. The description adds that it returns a JSON array of endpoint metadata with fields: operationId, summary, method, path. This provides valuable behavioral context beyond annotations.

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?

Three sentences: purpose & parameters, usage guidance, return value. No wasted words. Front-loaded with key information. Excellent structure for AI consumption.

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?

Tool is part of a broader discovery workflow; description links to `procore_discover_categories`. Return type is specified. Could mention pagination or rate limiting, but for a discovery tool that typically returns all results, this is sufficient. Adequate for agent to make informed decision.

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 100% with descriptions for all parameters. The description only summarizes filtering options ('free-text summary or HTTP method'), adding no significant nuance beyond the schema. Baseline 3 is appropriate.

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?

Clearly states the action (list), resource (Procore endpoints), and scope (within a category and optional module). Differentiates from siblings like `procore_discover_categories` and `procore_search_endpoints` by specifying the usage workflow. Mentions filtering options. The title and description align perfectly.

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?

Explicitly says to use after `procore_discover_categories` for focused drilling, providing a clear context. Mentions filtering by summary or HTTP method. Does not explicitly state when not to use or alternatives, but the workflow hint is strong enough for an agent.

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