github_billing_get_budget_org

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

The description implies a read operation but does not specify what data is returned (e.g., budget details, limits). With no annotations, the description is adequate but leaves some ambiguity about the response format.

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 clear sentence, very concise. However, it could be slightly expanded to improve usefulness without losing conciseness.

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?

No output schema exists, so the description should explain the return value (e.g., budget object with fields). It fails to do so. Also, with many sibling tools, a note on differentiation would be helpful.

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% but the descriptions are minimal ('org' and 'budget_id'). The description does not elaborate on how to obtain the budget_id or any constraints (e.g., format, where to find it). It adds no value beyond the schema.

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 action (Get) and the resource (a budget by ID for an organization). It distinguishes from sibling billing tools like get_all_budgets, update_budget, delete_budget, which deal with different operations on budgets.

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 provided on when to use this tool vs alternatives. For example, it does not mention that listing all budgets should use github_billing_get_all_budgets_org, or that updating requires the update tool.

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