get_business_registration_profile_by_agency

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

No annotations are provided, so the description carries full burden. It only says 'Get' but does not disclose that this is a read operation, whether pagination is involved, or any behavioral traits like rate limits or data freshness. The skip and top parameters imply pagination, but the description doesn't explain it.

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?

Single sentence that is front-loaded and efficient. However, it could be slightly more informative without sacrificing conciseness, e.g., mentioning that it returns a profile record and supports pagination.

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 tool with 4 parameters and no output schema, the description is too minimal. It does not explain what the response contains, how pagination works with skip/top, or any constraints on the agency code. The agent would need to infer behavior from parameter names alone.

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%, so the input schema already documents all parameters. The description mentions 'business number and agency' but adds no extra meaning beyond the schema definitions. Baseline 3 is appropriate as the description provides minimal added value.

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?

Description clearly states the verb 'Get' and resource 'business registration profile', specifying key parameters (business number and agency). However, it does not differentiate from sibling tools like get_business_registration_items_by_number or get_company_registration_master_by_number, which have overlapping functionality.

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 on when to use this tool versus alternatives. No mention of prerequisites, context, or scenarios. The description simply states what it does without any situational advice.

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