Objectives: Search

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

The description adds no behavioral information beyond what annotations already declare (readOnlyHint, idempotentHint, destructiveHint=false). It does not mention that the tool returns a list, supports pagination, or how search results are ordered, all of which would be helpful for an agent.

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 extremely short (3 words) but does not cover the tool's purpose adequately given the 16 parameters. It feels under-specified rather than concise. A more structured description could include search scoping, result format, or pagination hints.

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?

With 16 parameters, no output schema, and many sibling search tools, the description is woefully incomplete. It does not mention that this tool returns a list of objectives, how pagination works, or the logical relationship between filters. The agent lacks key information to use the tool effectively.

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 100%, so the baseline is 3. The description does not add any additional meaning or usage context for the parameters beyond what is already in the schema. No extra guidance on filter combinations or syntax.

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 'Find Shortcut objectives' clearly indicates the action (Find) and resource (Shortcut objectives). It distinguishes from 'objectives-get-by-id' by implying a search operation, but does not explicitly differentiate from similar sibling search tools, so it could be more precise.

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?

No guidance is provided on when to use this tool versus alternatives like 'objectives-get-by-id' or other entity-specific search tools. The description lacks context about prerequisites or typical use cases.

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