get_aibroadcast_status

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

The description aligns with annotations (readOnlyHint, destructiveHint, idempotentHint) and adds context: mentions HTTP GET method, zero side effects, and data retrieval. No additional behavioral traits beyond annotations, but adds value with method and safety emphasis.

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?

Extremely concise: five short sentences including emoji and method hint. No waste, front-loaded with purpose, and structured clearly.

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 read-status tool with one required parameter and no output schema, the description is adequate. It explains what it retrieves (status) and its effect (none), leaving minimal ambiguity.

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% and the single parameter 'Id' is clearly described as 'Request ID from AI broadcast creation'. The description does not add meaning beyond the schema, so 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 ('Get') and resource ('AI broadcast request status'), with explicit clarification that it fetches data and makes no changes. It distinguishes itself from sibling tools like 'create_aibroadcast' and 'update_aibroadcast'.

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?

Usage is implied as checking status after creating an AI broadcast, but no explicit when-to-use or when-not-to-use guidance is given. No alternatives are mentioned among the many sibling tools.

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