Query Managed Objects

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

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds minimal behavior disclosure beyond 'query', not explaining pagination, return format, or error conditions. With annotations present, the bar is lower, but the description still lacks useful behavioral 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 sentence, which is concise but lacks structure. It could benefit from bullet points or segmentation for clarity. It does not waste words, but the single sentence limits readability.

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?

The tool has 6 parameters, requires 1, and has no output schema. The description does not explain return values, pagination, or error behavior. The schema descriptions compensate partially, but the description alone is insufficient for complete understanding.

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?

All 6 parameters have descriptions in the schema (100% coverage). The description's mention of 'CREST query filter syntax' adds high-level context but does not provide additional parameter-level meaning 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?

The description clearly states the verb 'Query' and the resource 'managed objects' using CREST query filter syntax. However, it does not differentiate from sibling tools like listManagedObjects or getManagedObject, which also deal with managed objects.

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 itself does not provide usage guidelines, but the parameter descriptions for objectType and queryFilter give implicit prerequisites (use listManagedObjects to discover types, call getManagedObjectSchema first). No explicit when-to-use vs alternatives.

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